Change header level for included files (replacement PR) #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update README.md
Added hint for include together with citeproc
* Increase the header level of included files by 1, by using `include-indented` rather than just `include`. * Add example to test/input.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use
include-indentedor{ .include header-change=1}to increase the header level for included files.Also adds a
stack.yamland increments the release number to0.0.2.As to how it works, it carries an extra parameter for the change in header level, defaulting to 0, and applies it to every header block in the markdown files that get read in.
The use case is a set of files that can used alone or be included nested in a larger document.
The indenting option now includes the title of the included file as a header.
(This replaces #3 as it means I can use my develop branch)